Vehicle control system and mobile device used as vehicle key fob

ABSTRACT

An apparatus includes a vehicle control system (VCS) coupled to a computer of a vehicle via a CAN bus and configured to present selectively appearance of a presence in the vehicle of a smartkey, e.g., by energizing and de-energizing an actual smartkey of the vehicle. The VCS includes a VCS and a Bluetooth® VCS transceiver. The VCS stores VCS software. The apparatus also includes a smartphone with a Bluetooth® transceiver, and storing an app. The mobile device is paired with the VCS to communicate with the VCS via a Bluetooth® link. The app configures the smartphone to receive menu selections from a user, to generate communications that identity smartkey-enabled features of the VCS that correspond to the selections, and to send to the VCS the communications through the link. The VCS software configures the VCS to receive the communications and cause the vehicle to perform actions corresponding to live communications.

CROSS-REFERENCE TO RELATED APPLICATION

This application is a continuation of and claims priority to U.S. patentapplication Ser. No. 16/529,754, entitled VEHICLE CONTROL SYSTEM ANDMOBILE DEVICE USED AS VEHICLE KEY FOB, filed Aug. 1, 2019, now allowed.

FIELD OF THE DISCLOSURE

This disclosure relates generally to the field of vehicular and othersecurity, access, convenience, monitoring, and control products.

BACKGROUND

Vehicle control systems (“VCS”s) may be OEM and aftermarket electronicsystems installed in vehicles for monitoring, security, and users'convenience and entertainment, as well as for other reasons. Thefunctionality provided by such systems may include remote startcapability, passive keyless entry, passive locking, and other security,convenience, and monitoring features.

A need in the art exists for improved techniques for operating certainsecurity, convenience, and monitoring features of VCS-equipped vehicles,including operating the features with a mobile device such as asmartphone, without carrying a key, key fob, or analogous access device.A need in the art exists for providing temporary and/or limited accessto vehicles and their various features and compartments. Other needs inthe art will occur to a person skilled in the art alter careful perusalof this disclosure, claims, figures, and all other matter filed togetherwith this document.

SUMMARY

This document describes embodiments, variants, implementations, andexamples of novel techniques for addressing one or more of the needsidentified above, and/or other needs. Selected embodiments described inthis document include methods, apparatus, and articles of manufacturethat enable improved techniques of using a mobile device, such as asmartphone, as a vehicle key.

In an embodiment, an apparatus includes a vehicle control system and amobile device. The vehicle control system is coupled to vehicleelectronics of a vehicle via a vehicle bus. The vehicle control systemis configured to simulate presence in the vehicle of a smartkey of thevehicle. The vehicle control system includes one or more VCS processorsand a relatively short range radio frequency VCS transceiver. Thevehicle control system stores VCS software. The mobile device includesone or more mobile device processors and a relatively short range radiofrequency mobile device transceiver. The mobile device stores an app.The mobile device is configured to pair with the vehicle control systemto communicate with the vehicle control system via a communication linkbetween the relatively short range radio frequency mobile devicetransceiver and the relatively short range radio frequency VCStransceiver. When the app is executed by the one or more processors ofthe mobile device, the app configures the mobile device to receive menuselections from a user of the mobile device, to generate transmissionsthat identify smart key-enabled features of the vehicle control systemthat correspond to the selections, and to transmit to the vehiclecontrol system the transmissions through the communication link. Whenthe VCS software is executed by the one or more VCS processors, itconfigures the vehicle control system to receive the transmissions andcause the vehicle to perform actions corresponding to the transmissions.

In aspects, the vehicle bus is a CAN bus.

In aspects, the relatively short range radio frequency VCS transceiverand the relatively short range radio frequency mobile device transceiverare Bluetooth® transceivers.

In aspects, the smartkey-enabled features include engine start, vehiclelock, vehicle unlock, vehicle alarm activation, and/or vehicle alarmdeactivation.

In aspects, the vehicle control system is configured to simulate thepresence in the vehicle of the smartkey of the vehicle by sensing onlive vehicle bus smartkey challenges transmitted by the vehicleelectronics, and in response to the challenges transmit challengeresponses to the vehicle electronics through the vehicle bus.

In aspects, the vehicle control system is connected to one or moreantennae used by vehicle electronics to transmit smartkey challenges andreceive challenge responses, and the vehicle control system isconfigured to simulate the presence in the vehicle of the smartkey ofthe vehicle by sensing on the one or more antennae the smartkeychallenges, and in response to the challenges generate the challengeresponses and transmit the challenge responses to the vehicleelectronics through the one or more antennae.

In an embodiment, an apparatus includes a vehicle control systemconfigured to couple to a computer of a vehicle via a vehicle bus of thevehicle, and a mobile device. The vehicle control system includes one ormore VCS processors, a relatively short range radio frequency VCStransceiver, and a smartkey power control module (SPCM) configured toprovide to a smartkey of the vehicle electrical power selectively undercontrol of live one or more VCS processors, thereby selectively enablingand selectively preventing operation of smartkey-enabled features of thevehicle. The vehicle control system stores, in a memory, VCS softwareinstructions executable by the one or more VCS processors. The mobiledevice includes one or more mobile device processors and a relativelyshort range radio frequency mobile device transceiver. The mobile devicestores in its memory an app (instructions executable by the one or moremobile device processors). When the app is executed by the one or moremobile device processors, the app configures the mobile device to pairwith the vehicle control system to establish a communication linkbetween the relatively short range radio frequency mobile devicetransceiver and the relatively short range radio frequency VCStransceiver, to determine events associated with smartkey-enabledfeatures of the vehicle, an event per smartkey-enabled feature of thesmartkey-enabled features, to generate transmissions based on theevents, a transmission per event and to send to the vehicle controlsystem the transmissions through the communication link. When the VCSsoftware is executed by the one or more VCS processors, the VCS softwareconfigures the vehicle control system to pair with the mobile device toestablish the communication link, to receive the transmissions front themobile device, and for each of the transmissions received from themobile device to perform an action corresponding to the smartkey-enabledfeature associated with the event on which said each of thetransmissions is based. An event associated with a smartkey-enabledfeature is any occurrence that is designed to cause performance of asmartkey-enable feature, such as the user's selection on the smartphoneof a menu item designed to activate the feature (e.g. lock the vehicle,unlock the vehicle, arm the vehicle's security system, disarm thesecurity system, open close the vehicle's door(s)).

In aspects, the mobile device also includes at least one othertransceiver, for example, a cellular transceiver and a WiFi transceiver.

In aspects, the relatively short range radio frequency VCS transceiverand the relatively short range radio frequency mobile device transceiverare Bluetooth® transceivers.

In aspects, the smartkey-enabled features include an engine startfeature, a vehicle lock feature, a vehicle unlock feature, a vehiclealarm activation feature, and a vehicle alarm deactivation feature.

In aspects, some of the events are selections of menu items made by auser of the mobile device on the mobile device.

In aspects, the events include automatic detection of approach of themobile device to the vehicle.

In aspects, the events include automatic detection of departure of themobile device front the vehicle.

In aspects, the events include one or more passive keyless entry-relatedevents.

In aspects, the events include one or more automatic passiveaction-related events.

In aspects, the smartkey power control module is or includes a relay,such as an electromechanical or a solid state relay.

In aspects, the apparatus also includes the smart key secured in thevehicle control system or otherwise in the vehicle. The smartkey has apair of power input terminals, such as battery terminals. The relay mayinclude a pair of normally open contacts in series with the power inputterminals of the smartkey, so that the smartkey is energized when therelay is energized, and the smartkey is de-energized when the relay isde-energized.

In aspects, the vehicle control system is connected to one or moreantennae used by vehicle electronics to transmit smartkey challenges andreceive challenge responses, and the vehicle control system isconfigured to simulate the presence in the vehicle of the smartkey ofthe vehicle by sensing on the one or more antennae the smartkeychallenges, and in response to the challenges generate the challengeresponses and transmit the challenge responses to the vehicleelectronics through the one or more antennae.

In aspects, the mobile device also includes at least one othertransceiver.

In aspects, the mobile device also includes a cellular transceiver.

In aspects, the mobile device includes a user interface configured toreceive the menu selections from the user.

In an embodiment, a system includes a vehicle controller module such asa VCS controlling a vehicle and allowing door lock unlock control, a keyfob power controller commanded by the VCS, a short-range radio frequency(“RF”) transceiver connected through a wired or wireless connection tothe VCS, and a mobile phone that can communicate with the RFtransceiver. The system is configured so that upon the mobile phonebeing able to communicate with the RF transceiver, the VCS:

authenticates the mobile phone and identifies it as a valid/authorizedvehicle access token device,

detects that the user carrying the mobile phone is in proximity of thevehicle's doors,

unlocks one or more vehicle doors, and

enables the vehicle keyfob via the keyfob power controller, therebyallowing the user to enter and operate the vehicle.

In aspects, the VCS causes the vehicle's doors to lock in response tosensing that the mobile phone is beyond the proximity of the vehicle'sdoors.

In an embodiment, a system includes a vehicle controller module such asa VCS controlling a vehicle, allowing door lock unlock control, andsensing door handle controls. The system also includes a keyfob powercontroller commanded by the VCS. The system further includes ashort-range RF transceiver connected through a wired or wirelessconnection to the VCS. The system further includes a mobile phone thatcan communicate with the RF transceiver. The system is configured sothat upon the mobile phone being able to communicate with the RFtransceiver, the VCS:

authenticates the mobile phone identifies it as a valid vehicle accesstoken/device,

detects that the user earning the mobile phone is in proximity of thevehicle's doors,

in response to sensing a change in state of the door handle controls,unlocks one or more vehicle doors and enables the vehicle keyfob via thekeyfob power controller, thereby allowing the user to enter and operatethe vehicle.

In aspects, the VCS causes the doors to lock in response to sensing thatthe mobile phone is beyond the proximity of the vehicle's doors.

In an embodiment, a system includes a vehicle controller module such asa VCS controlling a vehicle and allowing door lock/unlock control, akeyfob power controller commanded by the VCS, a short-range RFtransceiver connected through a wired or wireless connection to the VCS,a second short-range RF transceiver connected through a wired orwireless connection to the VCS and supporting a larger range ofcommunication than the first short-range RF transceiver, and a mobilephone that can communicate with the RF transceivers. The system isconfigured so that upon the mobile phone being able to communicate withthe second longer-range RF transceiver.

the VCS authenticates the mobile phone and identifies it as a validvehicle access token device, and

in response to the mobile phone being able to communicate with the firstshorter-range RF transceiver, the VCS detects the user carrying themobile phone is in proximity of the vehicle's doors, unlocks one or morevehicle doors, and enables the vehicle keyfob via the keyfob powercontroller, thereby allowing the user to enter and operate the vehicle.

In aspects, the VCS causes the doors to lock in response to sensing thatthe mobile phone is beyond the proximity of the vehicle's doors.

In an embodiment, a system includes a vehicle controller module such asa VCS controlling a vehicle and allowing door lock unlock control, akeyfob power controller commanded by the VCS, a short-range RFtransceiver connected through a wired or wireless connection to the VCS,a second short-range RF transceiver connected through a wired orwireless connection to the VCS and supporting a larger range ofcommunication than the first short-range RF transceiver, and a mobilephone that can communicate with the RF transceivers. The system isconfigured so that upon the mobile phone being able to communicate withthe second longer-range RF transceiver, the VCS:

authenticates the mobile phone and identifies it as a valid vehicleaccess token device, and

in response to the mobile phone being able to communicate with the firstshorter-range RF transceiver, the VCS detects that the user carrying themobile phone is in proximity of the vehicle's doors, unlocks one or morevehicle doors, and enables the vehicle keyfob via the key fob powercontroller, thereby allowing the user to enter and operate the vehicle.

In aspects, the VCS causes the doors to lock in response to sensing thatthe mobile phone is beyond the proximity of the vehicle's doors.

In an embodiment, a system includes: a vehicle controller module suchits a VCS controlling a vehicle, allowing door lock unlock control, andsensing door handle controls: a keyfob power controller commanded by theVCS; a short-range RF transceiver connected through n wired or wirelessconnection to the VCS; a second short-range RF transceiver connectedthrough a wired or wireless connection to the VCS and supporting alarger range of communication than the first short-range RF transceiver;and a mobile phone that can communicate with the RF transceivers. Thesystem is configured so that upon the mobile phone being able tocommunicate with the second longer-range RF transceiver, the VCSauthenticates the mobile phone and identities it as a valid vehicleaccess token/device. The system is further configured so that upon themobile phone being able to communicate with the first shorter-range RFtransceiver, the VCS detects the user carrying the mobile phone is inproximity of the vehicle's doors, and in response to the VCS sensing achange in the state of the door handle controls, unlocks one or morevehicle doors and enables the vehicle key fob via the key fob powercontroller, thereby allowing the user to enter and operate the vehicle.

In aspects, the VCS causes the doors to lock in response to sensing thatthe mobile phone is beyond the proximity of the vehicle's doors.

Various features and aspects will be better understood with reference tothe following description, drawings, and claims.

BRIEF DESCRIPTION OF THE FIGURES

FIG. 1 illustrates selected steps of an exemplary smartphone-as-a-keyprocess, in accordance with selected aspects disclosed in this document;

FIG. 2A illustrates selected steps of an exemplary smartphone-as-a-keyprocess performed in response to activation of an engine start burton,in accordance with selected aspects disclosed in this document;

FIG. 2B illustrates selected steps of an exemplary smartphone-as-a-keyprocess that allows a menu selection by a user of a mobile device, inaccordance with selected aspects disclosed in this document;

FIG. 3 illustrates selected steps of an exemplary smartphone-as-a-keyprocess performed in response to activation of a panic button, inaccordance with selected aspects disclosed in this document;

FIG. 4 illustrates selected components of a vehicle control systems, inaccordance with selected aspects disclosed in this document;

FIG. 5A illustrates selected steps of an exemplary smartphone-as-a-keyprocess performed in response to activation of an engine start button,in accordance with selected aspects disclosed in this document;

FIG. 5B illustrates selected steps of another exemplarysmartphone-as-a-key process that allows a menu selection by a user of amobile device, in accordance with selected aspects disclosed in thisdocument;

FIG. 6A illustrates selected steps of an exemplary smartphone-as-a-keypassive keyless entry process, in accordance with selected aspectsdisclosed in this document;

FIG. 6R illustrates selected steps of an exemplary passive keylessvehicle locking process, in accordance with selected aspects disclosedin this document;

FIG. 7 illustrates selected steps of another exemplary passive keylessentry process, in accordance with selected aspects disclosed in thisdocument;

FIG. 8 illustrates selected steps of still another exemplary passive keyless entry process, in accordance with selected aspects disclosed inthis document; and

FIG. 9 illustrates selected steps of yet another exemplary passivekeyless entry process, in accordance with selected aspects disclosed inthis document.

DETAILED DESCRIPTION

The words “embodiment,” “variant,” “example,” “implementation,” andsimilar words and expressions as used in this document refer to aparticular apparatus, process, or article of manufacture, and notnecessarily to the same apparatus, process, or article of manufacture.Thus, “one embodiment” (or a similar word expression) used in one placeor context may refer to a particular apparatus, process, or article ofmanufacture; the same or a similar expression in a different place orcontext may refer to a different apparatus, process, or article ofmanufacture. The expression “alternative embodiment” and similar wordsand phrases may be used to indicate one of a number of differentpossible embodiments, variants, examples, or implementations. The numberof possible embodiments, variants, examples, or implementations is notnecessarily limited to two or any other quantity. Characterization of anitem as “exemplary” means that the item is used as an example. Suchcharacterization does not necessarily mean that the embodiment, variant,example, or implementation is a preferred one; the embodiment, variant,example, or implementation may but need not be a currently preferredembodiment, variant, example, or implementation. All embodiments,variants, examples, and implementations are described for illustrationpurposes and are not necessarily strictly limiting.

The words “couple,” “connect,” and similar words/expressions/phraseswith their inflectional morphemes, do not necessarily import animmediate or direct connection, but in addition to direct connectionsinclude within their meaning connections through mediate elements.

The expression “processing logic” should be understood as selectedsteps/decision blocks and/or hardware/software/firmware for implementingthe selected steps/decision blocks. “Decision block” means a step inwhich a decision is made based on some condition, and subsequent processflow is selected based on whether the condition is met or not met.

An “access point” or “entry point” may be, e.g., door, sunroof, hatch(rear or otherwise), trunk of a vehicle/building apartment/office, andother means for accessing a place or a thing.

“Passive keyless entry” or “PKE” refers to vehicle control systems thatcan be configured to unlock a vehicle automatically in response to anauthorized person approaching and being in proximity of the vehicle inwhich the system is installed. Some PKE-capable systems can beconfigured to unlock the vehicle in response to a door (or another entrypoint) handle of the vehicle being operated (e.g., pulled by the user).Some PKE-capable systems can be configured to unlock the vehicle inresponse to a door (or another entry point) handle touch or pull sensorsignal, or a button on the vehicle being pushed or otherwise activatedby the user. Some PKE-capable systems can be configured to lock thevehicle automatically in response to the user moving (e.g., walking)away from the vehicle. PKE-capable systems may be used with vehiclesother than passenger land vehicles, e.g., planes, boats, snow vehicles;and to secure structures or portions of structures, e.g., as part ofhome business security systems and locks. “Automatic” in reference to anaction, “automatic passive action” capability, and “APA” capabilityrefer to the capability of a system to take action automatically inresponse to a user with an authorized device approaching and/ordeparting a place or a thing, such as a predetermined location, avehicle, a building-structure or a predetermined portion of abuilding/structure. The action may be e.g.,locking/unlocking/opening/closing an access point or several accesspoints of a vehicle/building/apartment/office; operating lights of avehicle/building/apartment/office; operating horn or another sounddevice of a vehicle/building/apartment office; activating/deactivatingalarm of a vehicle/building/apartment office; turning on and offengines/appliances, climate control systems, and/or entertainmentdevices. Thus, a PKE-capable system is an APA-capable system. Theauthorized device may be a portable device, e.g., a key fob, asmartphone/tablet/computer, a smart watch, a wirelesscommunications-capable bio- or biometric implant, or another device.APA-capable and PKE-capable systems are described, for example, in U.S.Patent Application entitled SMARTPHONE BASED PASSIVE KEYLESS ENTRYSYSTEM, Michael S. Simmons inventor, Ser. No. 14/459,036, filed on orabout Aug. 13, 2014, U.S. Patent Application Publication Number2015/0048927: and in U.S. Patent Application entitled MULTI-SENSORPASSIVE KEYLESS FUNCTIONALITY, Aravind Warrior et. al., inventors, Ser.No. 16/401,704, filed on or about May 2, 2019. The above-referencedpatent applications and the related provisional application areincorporated herein by reference for all purposes, including theirspecifications, abstracts, figures, claims, and all other matter.

A vehicle control system (VCS) is generally (but not necessarilyexclusively) an aftermarket system installed in a vehicle to provideconvenience, security, and monitoring features, such as security systemfunctionality, PKE/APA, door unlocking and/or opening in response to aperson carrying a key or a key fob touching or moving door/hatch handlesor otherwise, door locking and/or closing, remote engine start,short-range radio frequency communications (Bluetooth® and other) withportable devices such as smartphones, tablets, smart implants, andsimilar functions. A VCS may be such as (or similar to, or havingselected components of) the vehicle control systems described in acommonly-owned U.S. Pat. No. 10,249,182 for REMOTE VEHICLE SYSTEMCONFIGURATION, CONTROL, AND TELEMATICS, James S. Turner first-namedinventor, which is incorporated herein by reference for all purposes,including specification, abstract, figures, claims, and all othermatter. A VCS may also be of another type.

A VCS installed in a vehicle may be connected to the Controller AreaNetwork bus (“CAN bus”) of the vehicle, and interface communicate withthe vehicle's electronics computer via the CAN bus. The VCS may alsosense CAN bus communications between and among the vehicle's electroniccomponents. Another type of bus interconnecting the vehicle'selectronics may take place of the CAN bus.

“Mobile device” (or simply “mobile”) and “portable device” are usedinterchangeably, to signify smartphones, smartwatches, tablets, smartimplants, portable computers, and similar portable devices. A mobiledevice typically includes a processing module (such asmicroprocessor(s), microcontroller(s), other programmable devices, andtheir memories and other supporting electronic component(s); a user I/Ointerface (such as a display/keyboard/touch-sensitive display); and oneor more transceivers (such as cellular transceivers, WiFi transceivers,Bluetooth® and other short-range radio frequency transceivers), andother devices.

Smart key und smart key fob may be referred to as “smartkey.” In typicaluse, the vehicle (vehicle computer, vehicle electronics) may send asignal (a “challenge”) to a smartkey, to determine whether the smartkeyis present inside the vehicle or in the immediate vicinity of thevehicle; when the smart key responds (by sending a “challengeresponse”), the vehicle (vehicle computer/electronics) may allow enginestart and/or operation of all or selected convenience and securityfeatures, such as locking unlocking the vehicle and aiming/disarming thevehicle's alarm. The smartkey's response may be static or, morecommonly, a result of a dynamic computation, e.g. to prevent spoofing.Some VCSs described in this document may be configured to sensechallenges, generate appropriate challenge responses (instead of thesmartkey), and send the challenge responses to the vehicle, thussimulating smartkey presence. Smartkeys are generally known in relationto use with cars and other vehicles, but analogous devices may be usedwith access, security, and convenience features of buildings andportions of buildings, including use with home/business security systemsand locks.

Some definitions have been explicitly provided above. Other and furtherexplicit and implicit definitions and clarifications of definitions maybe found throughout this document.

In embodiments, the VCS and/or the smartkey of the vehicle areconfigured to make it appear to the vehicle's electronics/computer thatthe functionality associated with the smartkey's presence should beenabled. For example, the smartkey may be placed in the vehicle, andsecured so that it cannot be readily found and/or removed; the smartkeymay be secured, for example, in the enclosure of the VCS. The vehicle'selectronics/computer would then be able to sense the presence of thesmartkey in the vehicle and allow engine start and or operation ofconvenience, security, and/or other features that require a smartkey ofthe vehicle to be inside or in the immediate vicinity of the vehicle(“smartkey-enabled features”). But the VCS connected to the vehicle'sCAN bus (or another analogous type of a bus interconnecting electronicsof the vehicle) can selectively prevent engine start and/or operation ofthe smartkey-enabled features. In this way, the security of the vehiclemay be preserved despite the presence of the smartkey in the vehicle,because the VCS can selectively (under control of the VCS processor,through the bus) enable and prevent engine start and operation of theother smartkey-enabled features.

In an embodiment, the VCS is configured to simulate selectively thepresence of the smartkey in or near the vehicle, by receiving from thevehicle's electronics the smartkey challenges, and generating theappropriate challenge responses, to make it appear to the vehicle'scomputer that the smartkey is present in or near the vehicle. Forexample, the VCS can receive the challenges from the CAN or analogousbus, and return appropriate challenge responses, also through the bus.In another example, the VCS may be connected through a transceiver tothe antenna that the vehicle's computer/electronics use to transmit thesmartkey challenges, and interpret the challenges actually sent by thevehicle electronics to the smartkey, unlike sensing the challengesthrough the bus. (The antenna here includes the wire connected to theantenna.) The VCS can then selectively (under control of the VCSprocessor) generate appropriate challenge responses to simulate thepresence of the smartkey in/near the vehicle, and drive the antenna withthese challenge responses. As has already been mentioned, the challengesand/or the responses may be static or dynamic; a dynamic response variesfrom time-to-time, location-to-location, challenge-to-challenge, and/orotherwise; the VCS and or the mobile device have (or can obtain)information for determining/computing an appropriate response to achallenge, for example, in the same way as the vehicle's smartkey would.

In an embodiment, the VCS includes a smartkey power control module forthe smartkey of the vehicle, the smartkey receives the electrical powerfor its operation when the VCS (under control of the VCS processor)determines that the operation of the smartkey-enabled features isallowed and/or required, and configures the smartkey power controlmodule so that the smartkey is energized. The smartkey power controlmodule may be an electrically-operated switch such as anelectromechanical or a solid state relay; it may be placed, for example,in series with the battery contacts (power inputs) of the smartkey. Whenthe smartkey power control module, under control of the VCS, turns onthe power to the smartkey in the vehicle, the vehicle electronics sensethe smartkey's presence and allow operation of the smartkey-enabledfeatures. The smart key may be, for example, secured to the vehicleand/or be placed inside the enclosure of the VCS or one of the modulesof the VCS, to make unauthorized removal difficult, the VCS isconfigured to turn the power to the smartkey on when needed to operateany of the smartkey-enabled features, such as the panic command, enginestart, door lock unlock, security features enable disable, and others.

The VCS in the vehicle may be configured to allow the engine startand/or operation of the other smartkey-enabled features in response tooperation of a “virtual key” tied to the user's mobile device. Thepresence of a mobile device previously configured to connect with andcontrol the VCS may be sufficient for the engine start and/or operationof the smart key-enabled features. The VCS may be configured torecognized mobile devices authorized to control the VCS and enable thesmartkey-enabled features. (Such authenticated mobile devices may bereferred to as “authorized mobile devices.”) The mobile device mayprovide an authorization code to the VCS over the connection, or berecognizable by the VCS based on the previously made connection. Forexample, the VCS may recognize the universally unique identifier(“UUID”) of the previously paired authorized mobile device, and allowoperation of the smartkey-enabled features. As another example, theauthorized mobile device may store a VCS authorization code and transmitit to the VCS over the connection, in response to being interrogated bythe VCS, in response to sensing the VCS over the connection, in responseto a command received from the user of the authorized mobile device, orotherwise. Once the VCS recognizes the authorized mobile device insidethe vehicle or within some predetermined distance of the vehicle (e.g.,as is described in the patent application Ser. No. 16/401,704, orotherwise), the VCS may enable automatic passive action such as passivekeyless entry, and/or the smartkey-enabled features. A special appinstalled in the authorized mobile device may need to be activated andrunning in the foreground to enable APA/PKE, engine start, and or othersmartkey-enabled features. The app may provide menu(s) to the user ofthe authorized mobile device to enable the user to control the enginestart and/or other selectable smartkey-enabled features through menu(s)or other inputs of the app executing on the mobile device. The user ofthe authorized mobile device (and of the vehicle) may control the enginestart and/or other selectable smartkey-enabled features through menu(s)or other inputs provided by the app executing on the mobile device.

Thus, the user carrying the authorized mobile device may approach thevehicle to within a short distance such as within a few feet (<10 feelin variants) and then be able to start the engine and/or operate theother smartkey-enabled features in a conventional manner applicable tothe vehicle, meaning in the same way as when the user is in possessionof the vehicle's OEM for replacement) smartkey. For example, the usermay pull on the door/hatch handle, and the VCS, sensing the operation ofthe door handle and near presence of the user's mobile device, mayunlock the door hatch or another entry point or multiple entry points;the user may press engine start push button while sitting in thevehicle, and in response the VCS may enable cause engine start; the usermay approach the vehicle to some predetermined distance or mobile devicesignal strength, and in response the VCS may automatically unlock thevehicle and/or turn off security alarm or other security features.Analogously, the VCS may sense that the user's authorized mobile deviceis beyond a predetermined distance and moving away from the vehicle (andor not being able to connect to the mobile device), and automaticallylock the vehicle and or turn on the vehicle's security system features.

FIG. 1 illustrates selected steps of a process 100 of an exemplarysmartphone-as-a-key (“SAAK”) implementation, performed by a systemincluding the combination of a vehicle-installed VCS and a user mobiledevice, each appropriately configured, respectively, by the VCS programcode and the program code of the SAAK app on the user mobile device. TheVCS may be connected to the CAN bus of the vehicle to sense when thevehicle's computer interrogates the smartkey by sending a challenge, andcan respond with an appropriate challenge response, which the VCSretrieves from its memory and/or computes. The VCS may also be connectedto the antenna that transmits the challenge and receives the challengeresponse, to receive the challenge and send back the appropriatechallenge response. The VCS may also include a smartkey power controlmodule connected to an actual smartkey of the vehicle, to energize thesmartkey when the VCS determines that smartkey-enabled functionalityshould be enabled.

At flow point 101, the VCS is installed in the vehicle,programmed/configured for operation, and powered-up; and the app forconfiguring the user mobile device for SAAK is downloaded to the usermobile device and activated, appropriately configuring the user mobiledevice to communicate with the VCS (and thus making the user mobiledevice an authorized mobile device). Configuring may include pairing theuser mobile device with the VCS, including storing the UUID of the VCSin the mobile device, and vice versa, so that the VCS UUID is registeredwith the operating system and/or the SAAK app of the mobile device, andthe UUID of the mobile device is registered with the VCS. Additionally,at the flow point 101, the user mobile device is not in the “sleep” orpower-conserving mode, and the app is running in the foreground. Forexample, if the user mobile device was in the sleep mode, when the usercarrying the user mobile device activates the app, the app causes theuser mobile device to exit the sleep mode and run the app in theforeground. As another example, the app wakes up when the user mobiledevice approaches the vehicle and the user mobile device senses theshort-range RF (e.g., Bluetooth®) transmissions from the VCS.

From the flow point 101, the process continues to step 105, in which theVCS detects the presence of the mobile device within a short distance ofthe vehicle. The VCS may use its Bluetooth® or similar short-range RFcommunications capability to detect the presence of the mobile deviceand estimate the vehicle's distance to the mobile device; for example,the distance estimate may be based on the strength of the RF signal fromthe mobile device, though other techniques are possible. In a variant,an action of the user of the mobile device causes the VCS to look forthe mobile device; the action may be, for example, the user's pulling ona handle of an entry point (e.g., the door handle of the vehicle), orthe user's pushing an external button on the vehicle (e.g. next to anentry point).

In step 110, the VCS interacts with the vehicle's electronics to causeperformance of an action (or actions, as the case may be) correspondingto the approach of the user, such as unlocking the vehicle or any of theentry points, turning off the alarm of the vehicle, etc. In embodiments,the interaction may include receiving the challenge from the vehicle'selectronics (computer) and sending an appropriate challenge response tothe vehicle's electronics, and sending a command to the vehicle'selectronics to perform the action(s). In examples, the interaction mayinclude enabling power to the smartkey through the smartkey powercontrol module connected to the VCS, and sending a command to thevehicle's electronics to perform the actions).

The process 100 may conclude at flow point 199.

One possible scenario following unlocking of the vehicle is when theuser pushes the engine start button of the vehicle. FIG. 2A illustratesselected steps of a process 200 of an exemplary operation of the systemin response to activation of the engine start button. The process 200begins at flow point 201, such as the state of the mobile device and theVCS after the vehicle is unlocked in the process 100.

In step 205, the electronics (computer) of the vehicle receives thestart command front the engine start button of the vehicle.

In step 210, the vehicle computer sends a smartkey challenge, to verifythat the smartkey is in the vehicle.

In step 215, the VCS detects the challenge. For example, the VCS maydetect the challenge through the antenna or the CAN bus (In thisembodiment, there might not be a smartkey stored in the vehicle, throughthe operation of the embodiment with the smartkey in the vehicle isanalogous, mutatis mutandis, here and in the other described processes.)

The VCS then generates a challenge response and sends it back to thevehicle computer, in step 220.

The vehicle electronics/computer receives the challenge response, instep 225, and causes engine start, in step 230.

The process flow may then terminate at flow point 249, and may berepeated as needed or desired.

Note that smartkey-enabled functions other than engine start may beperformed in response to the VCS receiving corresponding transmissionsfrom the mobile device with the app (which app may be referred to as“smartphone-as-a-key” or “SAAK” app). The process may be the same orsubstantially the same as the process 200, with the following variances.At the beginning of this modified process, the user of the authorizedmobile device selects a menu item corresponding to anothersmartkey-enabled feature (e.g., lock/unlock/arm/disarm), and the mobiledevice sends the transmission corresponding to the selected feature. TheVCS receives the transmission, and the vehicle electronics and/or theVCS activate the selected feature and perform the function(s) associatedwith the selected feature. FIG. 2B illustrates selected steps of aprocess 250 of an exemplary operation of the system in response to aselected feature sent by the mobile to the VCS. The feature may beselected through a menu-driven user interface, or otherwise.

Beginning with flow point 251, in which the mobile and the VCS areready, the process flow proceeds to step 255, in which the mobile appreceives user selection of a smartkey-enabled feature. The user mayinput the selection via a menu of the app.

In step 257, the mobile app generates a transmission corresponding tothe selected feature, for transmission to the VCS.

In step 260, the mobile app sends the transmission to the VCS, forexample, through a Bluetooth® or another short-range radio frequencycommunication link between the VCS and the mobile device.

In step 265, the VCS receives the transmission.

In step 270, the VCS instructs the vehicle computer to perform theaction corresponding to the selected smartkey-enabled feature. Forexample, the VCS may send a message to the vehicle computer through theCAN or analogous bus of the vehicle.

In step 275, the vehicle computer transmits a smartkey challenge, toverify the presence of the smartkey in or in the immediate vicinity ofthe vehicle. (Recall that the selected feature is a smartkey-enabledfeature.)

In step 280, the VCS detects the challenge, and in step 285 generatesand transmits back an appropriate challenge response. As has alreadybeen discussed, the VCS may receive the challenge and send the challengeresponse through the CAN or a similar bus of the vehicle, or through theantenna used by the vehicle electronics to communicate with thevehicle's smartkeys.

The vehicle computer receives the challenge response in step 290, and instep 295 performs the action corresponding to the feature, such aslocking/unlocking the vehicle, arming/disarming the vehicle's alarmsystem, and engine start.

The process 250 may then terminate at flow point 299, and may berepealed as needed or desired.

FIG. 3 illustrates selected steps of a process 300 of an exemplaryoperation of a smartkey-enabled panic button. At flow point 301, the VCSand the SAAK smartphone are ready, and the smartphone had beenpreviously associated (paired) with the VCS and is on authorized mobiledevice.

In step 305, the VCS receives from the smartphone a panic command sentin response to the user activating the panic function on the smartphone,such as touching a panic “button” on the screen of the smartphone.

In step 310, the VCS activates, either directly or through the vehicle'scomputer, panic function(s) of the vehicle, such as an alarm/siren.

In decision box 315, the VCS determines whether a command cancellingpanic has been received from the mobile; such command may be anotheractivation of the panic button or any other user-initiated commandthrough the SAAK app of the mobile. The process loops back until thepanic-cancelling command has been received.

Once the panic-cancelling command has been received, the processproceeds to step 320, in which the VCS cancels the alarm; again, the VCSmay be configured to perform this step directly or through the vehicle'scomputer.

The process flow may then terminate at flow point 399, to be repeated asneeded or desired.

FIG. 4 illustrates selected components of a Vehicle Control System 400that includes a smartkey power control module through which the VCSselectively energizes and de-energizes a smartkey of the vehicle inwhich the VCS is installed, and thus enables and disables thesmartkey-enabled features of the vehicle.

The VCS 400 includes a bus 405, a processing module 407, a memory module409, an interface or interfaces 410 to vehicle control modules, a remotestart module 415, an add-on security module 420, a relatively shortrange RF communication interface/transceiver(s) 425 to external devices,and a smartkey power control module (SPCM) configured to provideselectively electrical power to a smartkey 440. The smartkey 440 may beconsidered part of the VCS 400, or a separate component.

The bus 405 may be as a processor-based system bus that providescommunication networking capability between and among the components ofthe VCS 400. The processing module 407 may include, for example, amicroprocessor/microcontroller and supporting electronics. The memorymodule 409 can store instructions executable by the processing module407; the memory module 409 may include one or more memories of same ordifferent types, such as ROMs, PROMs, EPROMS, EEPROMS, flash memories,optical disks, magnetic storage devices, and/or other memories. Theinterface or interfaces 410 may connect to an engine computer (enginecontrol module or ECM); a transmission computer (transmission controlmodule or TCM); built-in vehicle firmware: built-in security features ofthe vehicle; a telematics module: and data storage for data thatincludes the vehicle's usage and performance data, such as OBD II data.The interface 410 may be a CAN bus interface. The remote start module415 allows starting of the vehicle by the VCS 400, in response toappropriate commands, for example, remote start commands received fromthe user mobile device 450. The remote start module 415 may alsointeract with the vehicle control modules through the interfaces 410accessible through the bus 405. The add-on security module 420 mayconnect to and monitor various sensors (e.g., shock vibration,proximity, intrusion, door or other entry point controls that indicatewhen the user is trying to open the entry point for access to thevehicle), and may operate and/or control various convenience features(e.g., power windows, power locks, power seats, steering wheeltelescoping and tilt positions, audio system presets and other audiosystem controls). The relatively short range RF communicationtransceiver(s) 425 can be, for example, a Bluetooth® interface. Thetransceiver(s) 425 may be another type of RF interface. Moreover,multiple relatively short range RF transceivers may be included. Thus, afirst transceiver and a second transceiver may be included, the firsttransceiver 425 having a shorter communication range than the secondtransceiver. For example, the transmit power of the first transceiver425 may be less than the transmit power of the second transceiver 425 bya factor of 2-20, with the two transceivers 425 being of the same type(such as Bluetooth®) or of different types; the first transceiver 425may be a Bluetooth® LE transceiver, while the second transceiver 425 maybe a non-LE Bluetooth®) transceiver.

FIG. 5A illustrates selected steps of a process 500 of an exemplaryengine start operation of the system in which a smartkey is connected tothe VCS through a smartkey power control module (SPCM). At flow point501 (such as the state of the mobile device and the VCS after thevehicle is unlocked in the process 100 or a similar process), theelectronics/computer of the vehicle receives the start command front thestart button of the vehicle, in step 505.

In step 506, the VCS also detects the start command. The VCS may detectthe start command, for example, through the CAN or analogous bus of thevehicle. The VCS and the vehicle electronics/computer may detect thestart command at the same or substantially same time.

In step 507, the VCS energizes the smartkey through the smartkey powercontrol module. For example, the processor of the VCS under control ofprogram code applies a relay control voltage to the SPCM to close relaycontacts (which may be normally open) and complete the circuit thatpowers the smartkey instead of the battery.

In step 510, the vehicle electronics send a challenge, to verify thatthe smartkey is in the vehicle.

In step 520, the smartkey (which is now energized) receives thechallenge and responds with an appropriate smartkey challenge response.

The vehicle electronics/computer receives the challenge response, instep 525, and starts the engine, in step 530.

Once the engine has started, the VCS de-energizes the smartkey, in step535, so that the SPCM stops providing power to the smartkey. Invariants, this step is skipped, at least as long as the vehicle's engineis operating.

The process flow may then terminate at flow point 549, and may berepeated as needed or desired.

FIG. 5B illustrates selected steps of a process 550 in whichsmartkey-enabled functions are performed in response to the VCSreceiving corresponding commands transmissions from the mobile devicewith the SAAK app, and the VCS is connected to a smartkey through asmartkey power control module.

Beginning with flow point 551, in which the mobile and the VCS areready, the process flow proceeds to step 555, in which the mobile appreceives user selection of a smartkey-enabled feature, such aslock/unlock the vehicle, activate/deactivate alarm of the vehicle, startengine of the vehicle. The user may input the selection via a menu ofthe app.

In step 557, the mobile/app generates a transmission corresponding tothe selected feature, for sending to the VCS.

In step 560, the mobile/app sends the transmission to the VCS, forexample, through a Bluetooth® or another short-range radio frequencycommunication link between the mobile device and the VCS.

In step 565, the VCS receives the transmission.

In step 570, the VCS energizes the smartkey through the smartkey powercontrol module. For example, the processor of the VCS under control ofthe VCS software applies voltage to the SPCM to close the normally openrelay contacts and complete the circuit that powers the smartkey insteadof the battery.

In step 575, the VCS instructs the vehicle computer to perform theaction(s) corresponding to the selected feature. For example, the VCSmay do so through the vehicle CAN bus.

In step 580, the vehicle computer transmits a smartkey challenge, toverify the presence of the smartkey in or in the immediate vicinity ofthe vehicle. (Recall that the selected feature is a smartkey-enabledfeature.)

In step 585, the smartkey (which is now energized) receives thechallenge and responds with an appropriate smartkey challenge response.

The vehicle computer/electronics receives the challenge response, instep 590, and performs the action(s) corresponding to the selectedfeature, in step 595. For example, the vehicle computer may lock/unlockthe vehicle, arm/disarm the vehicle's alarm, start the vehicle's engine.

The process 550 may then terminate at flow point 599, and may berepeated as needed or desired.

FIG. 6A illustrates selected steps of a process 600 of an exemplarypassive keyless entry operation of the system in which a smartkey isconnected to the VCS through a smartkey power control module (SPCM). Atflow point 601, the VCS and the user mobile device such as a SAAKsmartphone are ready, and the smartphone had been previously associated(paired) with the VCS.

In step 605, the VCS and the smartphone establish a communication linkusing their short range transceivers, such as Bluetooth® transceivers.Once the link is established, the VCS authenticates the smartphone as anauthorized mobile device for the vehicle controlled by the VCS, in step610. The VCS then checks whether the smartphone is sufficiently near thevehicle to unlock the vehicle, in decision block 615, and loops backuntil the condition for unlocking the vehicle is met. After thecondition has been met (estimated vehicle-smartphone distance is shorterthan a predetermined limit, the power transmitted by the Bluetooth®transceiver of the smartphone exceeds some predetermined power limit,and/or otherwise as described in this document and the incorporateddocuments), the process flow advances to step 620. In the step 620, theVCS operates the SPCM to energize the smartkey of the vehicle. In step625, the VCS unlocks one or more entry points (doors, etc.) of thevehicle. The VCS may unlock the vehicle directly or instruct the vehiclecomputer to unlock the vehicle. The process flow then terminates at flowpoint 649, to be repeated as needed or desired.

FIG. 6B illustrates selected steps of a process 650 of an exemplarypassive keyless vehicle locking operation. At flow point 651, thevehicle may be unlocked, and the VCS is ready. In decision block 660,the VCS checks whether the smartphone is sufficiently far from thevehicle to lock the vehicle; this may be the case, e.g., if noBluetooth® link can be established with the mobile device, if theestimated distance to the vehicle is greater than some predetermineddistance limit, or if the power transmitted by the Bluetooth®transceiver of the smartphone is below some predetermined power limit.Once the VCS determines that the smartphone is far enough to lock thevehicle, the VCS operates the SPCM to energize the smartkey of thevehicle, in step 665, and locks the vehicle, in step 670. The VCS maylock the vehicle directly or instruct the vehicle's computer to lock thevehicle. The VCS may then operate the SPCM to de-energize the smartkey,in step 675. The process flow then terminates at flow point 699, to berepeated as needed.

FIG. 7 illustrates selected steps of a process 700 of an exemplarypassive keyless entry operation of the system in which a smartkey isconnected to the VCS through a smartkey power control module, and thevehicle is equipped with door handle sensors. At flow point 701, the VCSand the smartphone are ready, and the smartphone had been previouslyassociated with the VCS.

In step 705, the VCS and the smartphone establish a communication linkusing their short range transceivers, such as Bluetooth® transceivers.Once the link is established, the VCS authenticates the smartphone as anauthorized mobile device for the vehicle controlled by the VCS, in step710. In the loop created by decision block 712, the VCS monitors theentry point (such as door) sensors, detecting when the entry point (doorhandle) sensors are activated in an apparent attempt to enter thevehicle. Once a door sensor is activated, the process flow advances todecision block 715, where the VCS checks whether the smartphone issufficiently near the vehicle to unlock the vehicle, and loops backuntil the condition for unlocking the vehicle is met. After thecondition has been met (estimated vehicle-smartphone distance is longerthan a predetermined limit, the power transmitted by the Bluetooth®transceiver of the smartphone is below some predetermined power limit,and/or otherwise as described in this document and the incorporateddocuments), the process flow advances to step 720. In the step 720, theVCS operates the SPCM to energize the smartkey of the vehicle. In step725, the VCS unlocks one or more entry points (doors, etc.) of thevehicle. The process flow may then terminate at flow point 749, to berepeated as needed or desired.

FIG. 8 illustrates selected steps of a process 800 of an exemplarypassive keyless entry operation of the system in which a smartkey isconnected to the VCS through a smartkey power control module, and theVCS includes two relatively short range RF transceivers, the firsttransceiver having a longer communication range than the secondtransceiver.

At flow point 801, the VCS and the smartphone are ready, and thesmartphone had been previously associated (paired) with each of the twotransceivers of the VCS. In step 805, the VCS and the smartphoneestablish a communication link using the first (longer range)transceiver of the VCS. Once this link (“link1”) is established, the VCSthrough link1 authenticates the smartphone as an authorized mobiledevice for the vehicle controlled by the VCS, in step 810. In step 815,the VCS attempts to establish “link2” with the smartphone using thesecond (shorter range) transceiver. In decision block 820, the VCSdetermines whether link2 has been successfully established. If not, theprocess flow loops back to the step 815. Once link2 has beenestablished, the VCS proceeds to determine whether live smartphone issufficiently near the vehicle to unlock one or more entry points of thevehicle, in decision block 825. When the smartphone is sufficiently nearthe vehicle, the VCS operates the SPCM to energize the smartkey, in step830, and unlocks one or more entry points of the vehicle, in step 835.The process flow may then terminate at flow point 899, to be repeated asneeded.

FIG. 9 illustrates selected steps of a process 900 of an exemplarypassive keyless entry operation of the system in which a smartkey isconnected to the VCS through a smartkey power control module, the VCSincludes two relatively short range RF transceivers with the firsttransceiver having a longer communication range than the secondtransceiver, and the vehicle is equipped with door handle sensors.

At flow point 901, the VCS and the smartphone are ready, and thesmartphone had been previously associated (paired) with each of the twotransceivers of the VCS. In step 905, the VCS and the smartphoneestablish a communication link using the first (longer range)transceiver of the VCS. Once this link (“link1”) is established, the VCSthrough link1 authenticates the smartphone as an authorized mobiledevice for the vehicle controlled by the VCS, in step 910. In step 915,the VCS attempts to establish “link2” with the smartphone using thesecond (shorter range) transceiver. In decision block 920, the VCSdetermines whether link2 has been successfully established. If not, theprocess flow loops back to the step 915. Once link2 has beenestablished, the process advances to the loop created by decision block922, where the VCS monitors the entry point (such as door) sensors,detecting when the entry point (door handle) sensors are activated in anapparent attempt to enter the vehicle. When an entry point sensor isactivated, the process advances to decision block 925, where the VCSchecks whether the smartphone is sufficiently near the vehicle to unlockthe vehicle, and loops bock until the condition for unlocking thevehicle is met. After the condition has been met (e.g., estimatedvehicle-smartphone distance is longer than a predetermined limit, thepower transmitted by the Bluetooth® transceiver of the smartphone isbelow some predetermined power limit, and/or otherwise as described inthis document and the incorporated documents), the process advances tostep 930. In this step, the VCS operates the SPCM to energize thesmartkey. The VCS then unlocks (directly or through the vehicle'scomputer) one or more entry points of the vehicle, in step 935. Theprocess flow may then terminate at flow point 99, to be repealed asneeded.

In another application, the VCS is associated/paired with multiplemobile devices. For example, the VCS of the vehicle max beassociated/paired with two or more smartphones of family members. Inanother example, the app on the user's smartphone (or on multiplesmartphones with sufficient authorization) may create a “valet key” as adigital token that can be sent to another smartphone. The valet key maybe sent via email, text, Near Field Communication, user smartphoneapp-to-valet smartphone app communications, or in another way. The othersmartphone may have an app such as the app on the user's smartphone, oranother app with similar capability. When the other smartphone sends thetoken to the VCS of the vehicle, for example, through a Bluetooth® oranalogous relatively-short range link, the VCS may allow full or limitedaccessibility of the other smartphone to the vehicle and or full limitedperformance of the vehicle. For example, the valet key, when used, maydictate that the VCS of the vehicle prevent access to the vehicle'strunk and glove compartment, and to the vehicle's wireless communicationsystem so that it will not be used to make calls and send messages thatappear to come from the user/owner of the vehicle. The VCS may alsolimit power available from the engine motor of the vehicle. The valetkey may also be limited geographically, for example, based on GPSposition of the vehicle. The valet key may be set to expire at a presetor user-selected time (or after a predetermined or user-defined period);once expired, the valet key will no longer allow access to the vehicle.In this way, the use of the user's smartphone as a key may be extendedto valet and other attendants, without requiring the user to part withthe smartphone and entrust it to the valet.

This document and the attached Figures describe a VCS and a mobiledevice configured to replace a vehicle key. In specific embodiments, aVCS senses the presence of the authorized mobile device and takesautomatic action in response to its approach and or departure, allowssmartkey-enabled features to operate when the SAAK user sendsappropriate commands from the authorized mobile device, and/or allowssmartkey-enabled functions to be performed when the user operates thevehicle (such as engine start). It should be noted, however, that notall of the functionality need to be present in the same system. Moregenerally, not every illustrated described step and decision block maybe required in every embodiment in accordance with the conceptsdescribed in this document, while some steps and decision blocks thathave not been specifically illustrated may be desirable or necessary insome embodiments in accordance with the concepts. The process steps anddecisions may be performed by same and or separate elements, inconjunction or in parallel, asynchronously or synchronously, in apipelined manner, or otherwise. There is no particular requirement thatthe steps and decisions be performed in the same order in which thisdescription lists them and/or the Figures show them, except where aspecific order is inherently required, explicitly indicated, or isotherwise made clear from the context. Specific embodimentsvariants/examples/implementations, however, use the particular order(s)in which the steps and decisions (if applicable) are shown and/ordescribed. The features (elements/steps limitations) describedthroughout this document, the attached Figures, and the incorporateddocuments may be present individually, or in any combination orpermutation, except where the presence or absence of specific featuresis inherently required, explicitly indicated, or is otherwise made clearfrom the description and the drawings. This applies whether or not thefeatures appear related to specific embodiments; in other words,features of one described or illustrated embodiment (of this documentand the incorporated documents) may be included in another described orillustrated embodiment.

The instructions (machine executable code) corresponding to the methodsteps of the disclosed embodiments, variants, examples, andimplementations may be embodied directly in hardware, in software, infirmware, or in combinations thereof. A software module may be stored involatile memory, flash memory, Read Only Memory (ROM), ElectricallyProgrammable ROM (EPROM), Electrically Erasable Programmable ROM(EEPROM), hard disk, a CD-ROM, a DVD-ROM, or other form ofnon-transitory storage medium. Exemplary storage medium or media may becoupled to one or more processors so that the one or more processors canread information from, and write information to, the storage medium ormedia. In an alternative, the storage medium or media may be integral toone or more processors.

This document describes in detail the inventive apparatus, methods, andarticles of manufacture for use of a smartphone or another mobile deviceas a key. This was done for illustration purposes and therefore, theforegoing description is not necessarily intended to limit the spiritand scope of the invention(s) described. Neither the specificembodiments of the invention(s) as a whole, nor those of its (or their,as the ease may be) features necessarily limit the general principlesunderlying the invention(s). The specific features described herein maybe used in some embodiments, but not in others, without departure fromthe spirit and scope of the inventions) as set forth herein. Variousphysical arrangements of components and various step sequences also fullwithin the intended scope of the invention(s). Many additionalmodifications are intended in the foregoing disclosure, and it will beappreciated by those of ordinary skill in the pertinent art that in someinstances some features will be employed in the absence of acorresponding use of other features. The embodiments described above areillustrative and not necessarily limiting, although they or theirselected features may be limiting for some claims. The illustrativeexamples therefore do not necessarily define the metes and bounds of theinventions) and the legal protection afforded the invention(s).

What is claimed is:
 1. A vehicle control system (VCS) of a vehicle,comprising: one or more VCS processors; memory coupled to the one ormore VCS processors and storing VCS software executable by the one ormore VCS processors; a smartkey power control module (SPCM) configuredto provide selectively electrical power to a smartkey of the vehicleunder control of the one or more VCS processors executing the software,wherein, when the SPCM is providing electrical power to the smartkey,operation of smartkey-enabled features of the vehicle is enabled andwhen the SPCM is not providing electrical power to the smartkey,operation of the smartkey-enabled features of the vehicle is notenabled; and a radio frequency (RF) transceiver coupled to the one ormore VCS processors; wherein, when the VCS software is executed by theone or more VCS processors, the VCS software configures the VCS to:recognize an authorized mobile device through an RF communication linkbetween the RF transceiver and the authorized mobile device, theauthorized mobile device being authorized to access one or more of thesmartkey-enabled features of the vehicle, and detect when the authorizedmobile device is within a first predetermined distance of the vehicle;and configure the SPCM to provide electrical power to the smartkey andenable access to the one or more of the smartkey-enabled features of thevehicle through the authorized mobile device, in response to thepresence of the authorized mobile device within the first predetermineddistance of the vehicle.
 2. The vehicle control system of claim 1,further comprising an interface to vehicle control modules of themodules, the vehicle.
 3. The vehicle control system of claim 2, whereinthe interface to vehicle control modules is a CAN bus interface, the VCSfurther comprising an enclosure containing the one or more VCSprocessors, the memory, the SPCM, and the interface.
 4. The vehiclecontrol system of claim 3, further comprising a remote start module forthe vehicle.
 5. The vehicle control system of claim 4, furthercomprising an add-on security module connecting the vehicle controlsystem to one or more security sensors installed in the vehicle.
 6. Thevehicle control system of claim 5, wherein the one or more sensors areselected from the group consisting of shock/vibration sensors, proximitysensors, intrusion sensors, and entry point control sensors.
 7. Thevehicle control system of claim 4, further comprising an add-on securitymodule connecting the vehicle control system to one or more conveniencefeature devices installed in the vehicle.
 8. The vehicle control systemof claim 7, wherein the one or more convenience feature devices areselected from the group consisting of power windows, power locks, powerseats, steering wheel telescoping and tilt positioning devices, and anaudio system.
 9. The vehicle control system of claim 4, wherein the SPCMcomprises means for selectively enabling and disabling the smartkey. 10.The vehicle control system of claim 4, wherein the SPCM comprises arelay configured to provide selectively electrical power to thesmartkey.
 11. The vehicle control system of claim 4, further comprisingthe smartkey coupled to the SPCM.
 12. The vehicle control system ofclaim 11, wherein the one or more of the smartkey-enabled features ofthe vehicle comprise remote start of the vehicle.
 13. A method ofoperating features of a vehicle, the method comprising steps of:installing a vehicle control system (VCS) in the vehicle, the VCScomprising a smartkey of the vehicle and a smartkey power control module(SPCM) configured to provide selectively electrical power to thesmartkey of the vehicle under control of one or more processors of theVCS, the SPCM in a first state connecting electrical power to thesmartkey to energize the smartkey, the SPCM in a second state preventingelectrical power from energizing the smartkey; and installing an app ona mobile device, the app configuring the mobile device to pair with theVCS, to be recognized as a valid mobile device that is authorized toaccess smartkey-enabled features of the vehicle, and to enable a user ofthe valid mobile device to send one or more smartkey commands from thevalid mobile device to the VCS to operate the smartkey-enabled featureswhen the valid mobile device is within a first predetermined distance ofthe vehicle.
 14. The method of claim 13, further comprising sending asmartkey command of the one or more smartkey commands from the validmobile device to the VCS when the valid mobile device is within thefirst predetermined distance of the vehicle, the smartkey commandcorresponding to a first smartkey-enabled feature of thesmartkey-enabled features of the vehicle.
 15. The method of claim 14,further comprising: receiving the smartkey command by the VCS; and inresponse to receiving the smartkey command by the VCS, placing the SPCMin the first state and operating the first smartkey-enabled feature ofthe vehicle.
 16. The method of claim 13, further comprising: sending aremote start command from the valid mobile device to the VCS when thevalid mobile device is within the first predetermined distance of thevehicle; receiving the remote start command by the VCS; and in responseto receiving the remote start command by the VCS, placing the SPCM inthe first state and performing a remote start of the vehicle.
 17. Themethod of claim 13, further comprising: detecting by the VCS an approachof a user carrying the valid mobile device to within the firstpredetermined distance of the vehicle; and in response to detection ofthe approach, placing the SPCM in the first state.
 18. The method ofclaim 13, further comprising: detecting by the VCS an approach of a usercarrying the valid mobile device to within the first predetermineddistance of the vehicle; and in response to detection of the approach,placing the SPCM in the first state and unlocking the vehicle.